Skip to content

Conversation

@olevski
Copy link
Member

@olevski olevski commented Dec 2, 2025

depends on #781

/deploy

Adds a retry to the oidc discovery which can fail when reunku is upgraded or is installed for the first time because keycloak takes a while to start up fully.

@olevski olevski requested a review from a team as a code owner December 2, 2025 10:37
@RenkuBot
Copy link
Contributor

RenkuBot commented Dec 2, 2025

You can access the deployment of this PR at https://renku-ci-gw-782.dev.renku.ch

@olevski olevski force-pushed the chore-retry-keycloak-client-init branch from ada9f37 to 08a4a8d Compare December 2, 2025 10:41
This makes it so that if other services are not immediately available
when the gateway starts, the gateway will not immediately go into
@olevski olevski force-pushed the chore-retry-keycloak-client-init branch from 08a4a8d to 7baeae8 Compare December 2, 2025 14:22
Copy link
Member

@leafty leafty left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@olevski
Copy link
Member Author

olevski commented Dec 3, 2025

Should we also update the helm chart to make use of startup probes?

Yes that should help and I can open a followup PR to this.

@olevski olevski requested a review from leafty December 3, 2025 12:45
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants